Add async payments: blog post + implementation guide with shared diagram#314
Open
ConorOkus wants to merge 5 commits into
Open
Add async payments: blog post + implementation guide with shared diagram#314ConorOkus wants to merge 5 commits into
ConorOkus wants to merge 5 commits into
Conversation
✅ Deploy Preview for lightningdevkit ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Separate the async payments material into a conceptual blog post (authored by Matt Corallo & Valentine Wallace) covering the challenge, existing approaches, and protocol design, and a trimmed implementation guide focused on integration for each node role. The two pages cross-link each other. Add a shared AsyncPaymentsSequenceDiagram component (registered globally) embedded in both pages so they stay in sync. The diagram is a 2x render of the sequence view, and is click-to-zoom via a self-contained lightbox (Escape / click to close, SSR-safe). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Render a dark-palette variant of the sequence diagram and swap between
the two via CSS keyed on VitePress's `html.dark` class (set before paint,
so no theme flash). Applies to both the inline figure and the lightbox.
Fix a specificity bug where the shared `img { display: block }` rule
outranked the per-image hide rule, leaving both variants visible in
light mode. Visibility is now driven purely off the per-image classes.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
de848d9 to
b3927b0
Compare
The sender-side HTLC hold (extending CLTVs so the sender's LSP can hold the payment until the recipient returns) has not been merged yet, so the feature is not production-ready and the APIs may still change. Flag this up front with a beta callout. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add the interoperability caveat to the beta warning: the flow currently works between LDK nodes and is not yet guaranteed to interoperate with other Lightning implementations. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Splits the async payments material into two complementary pieces, sharing a single diagram component.
What's here
docs/blog/async-payments-receiving-while-offline.md(authored by Matt Corallo & Valentine Wallace): the conceptual narrative — the challenge of receiving while offline, existing approaches and their limitations, how the protocol works, and design notes.docs/async-payments.md(under Advanced Guides): trimmed to the implementation — integration steps for always-online, often-offline, and LSP / static-invoice-server roles.Diagram
AsyncPaymentsSequenceDiagram.vuecomponent, registered globally and embedded in both pages so they stay in sync.html.darkclass (no theme flash).🤖 Generated with Claude Code